feat(review-reminders): edge to edge support - #21582
Conversation
|
Snapshot diff report vs
All 6 changed screenshotsReviewRemindersScreenshotTest
|
This comment was marked as resolved.
This comment was marked as resolved.
e0780d1 to
b42c9cf
Compare
b42c9cf to
74918b8
Compare
|
Investigating: FixedSnackbar should use the inset. EDIT: This is screenshot-only
Bad alignment of the text and the back arrow
@ericli3690 I feel this one is better
|
072d90b to
f3e14a0
Compare
|
@david-allison Regarding the screenshot comparison you've annotated with "I feel this one is better": I do agree the padding change looks fine. I'm curious though if it's inconsistent with the title padding on the other Settings screens (ex. Reviewing, General). In particular, does the title padding noticeably change when transitioning from the Schedule Reminders page to the Troubleshooting page? If not then LGTM on that front Will do a full review of this PR starting now Edit: unit tests failing with legitimate failure |
f3e14a0 to
010e7e7
Compare
|
Fixed, sorry! |
ericli3690
left a comment
There was a problem hiding this comment.
LGTM!! Thanks for taking this on, really appreciate it. Tested on my phone and tablet and it looks good. Ping me on the Settings / Preferences + SingleFragmentActivity e2e migrations when they're ready and I'll take a look at those too, thanks thanks
|
Cheers! I don't want to mark this as awaiting my reply, but I'd like to get to these nitpicks before merge |
The fragments now unconditionally fit the system windows: the host activities consume the insets. Issue 17334 Part of 21519 Assisted-by: Claude Fable 5
Part of 17334 Part of 21519 Assisted-by: Claude Fable 5
* Removes the black bar in landscape mode * Troubleshooting content renders underneath the bottom bar Part of 17334 Part of 21519 Assisted-by: Claude Fable 5
The content of the toolbar in landscape mode of a phone overlapped with the display cutout. Part of 17334 Assisted-by: Claude Fable 5
The decor consumed the navigation bar inset, so scrolled content did not render underneath the nav bar. Part of 17334 Fixes 21519 Assisted-by: Claude Fable 5
BaseTransientBottomBar uses the deprecated `systemWindowInsets` accessors which include the display cutout on a real device. In tests, we manually add the cutout to the navigationBars() to simulate this Part of 17334 Part of 21519 Assisted-by: Claude Fable 5
010e7e7 to
79c9309
Compare
|
@ericli3690 handled, re-review if you wish |
ericli3690
left a comment
There was a problem hiding this comment.
Yep, looks awesome to me! Thanks thanks again



Note
Assisted-by: Claude Fable 5
Purpose / Description
ScheduleRemindersFragmentandReminderTroubleshootingFragmentneeded edge to edge supportFixes
ScheduleRemindersFragment#21519Approach
Before starting, consume the insets which will be passed to the fragments, then set the insets on a per-element basis.
There was lots of experimentation here to get the screenshots working correctly (ensuring the toolbars extended into the cutouts, ensuring scrolling), each is split into a separate commit.
I have a follow-up implemented for 'Settings', but this PR is already too large:
How Has This Been Tested?
Screenshot tests are added.
API 37
Learning
FragmentHostmade this difficultChecklist